Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

TPO 2029

reference
56-tree-1
name
TPO 2029
tree-preservation-order

undefined

56-tpo-1
uprn
address-text
point
POINT (-0.980676 50.816739)
geometry
MULTIPOLYGON (((-0.980620 50.816733,-0.980622 50.816744,-0.980630 50.816754,-0.980642 50.816762,-0.980658 50.816768,-0.980676 50.816769,-0.980693 50.816768,-0.980709 50.816763,-0.980722 50.816755,-0.980730 50.816745,-0.980733 50.816734,-0.980731 50.816723,-0.980723 50.816713,-0.980710 50.816705,-0.980695 50.816699,-0.980677 50.816697,-0.980660 50.816699,-0.980644 50.816704,-0.980631 50.816712,-0.980623 50.816722,-0.980620 50.816733)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL